I've been playing around with getting the demo working on a WinCE GPS device (actually the Airspace Aware device), and one limitation is the fact that the launch .exe file has to have a particular name. It works fine when I rename SkyDemon.exe but then the sync function from the laptop won't find the software properly. I've ended up having to have two copies of the .exe file with different names to get around this.



Would there be any way to uncouple the name of the .exe file from the sync function? Would probably help the app to work on lots more WinCE devices that have similar filename requirements.

SkyDemon Plan searches for SkyDemon.exe on the device to determine the installation location. Your idea of having two executables would seem to do the trick, in the absence of a better way of checking for installation location.

There is a better way to run SkyDemon on AWARE!  Try the following ......

Put inflight onto an SD card using the SD method

Switch on AWARE with SD card removed

Insert SD card once AWARE is booted up to original device menu page

Click settings

On settings page click the arrow (for more options)

Click Nav Path

Click the ...... path box

double click Sky Demon folder

double click SkyDemon.exe file

click save button 

close setting page

click GPS button on front page to run SkyDemon

activesync runs perfectly!

NB - reversion to run AWARE saftware is just a repeat of above but select FreedomCE.exe

Click

Doober, that is an option, of course, but it seems far easier to be able to just swap the SD cards and have it just work!



Tim, all I was wondering was if the software could look for a different file in the installation. Not that it matters much having two copies of the executable with different names (Shame windows doesn't do hard links like unix really!)

There's really no reason why we should look for anything other than SkyDemon.exe, since we're looking for SkyDemon.

Windows actually does both hard and soft links brilliantly, but not (I don't think) on device storage cards.

I guess I'm thinking from a unix background where checking for library or header files or even md5 checksums would be a more usual way (I think) of checking for a software location. It doesn't really matter though, it's my own fault for re-using kit not designed to run an arbitary .exe filename (although I'm sure there are many devices out there which are the same).



It's a limitation of the FAT filesystems on SD cards that prevents hard linking. I never knew that other Windows filesystems could do filesystem links!